Skip to content

fix(deps): pin AngleSharp to 1.5.2 to clear mXSS advisory#106

Merged
andregoepel merged 2 commits into
mainfrom
fix/anglesharp-mxss-advisory
Jul 18, 2026
Merged

fix(deps): pin AngleSharp to 1.5.2 to clear mXSS advisory#106
andregoepel merged 2 commits into
mainfrom
fix/anglesharp-mxss-advisory

Conversation

@andregoepel

Copy link
Copy Markdown
Owner

Problem

bunit 2.7.2 pulls AngleSharp 1.4.0 transitively (via AngleSharp.Diffing) into the Blazor test project. That version has a moderate mXSS advisoryGHSA-pgww-w46g-26qg / CVE-2026-54570 (improper MathML <annotation-xml> handling, sanitizer bypass), patched in 1.5.0.

The CI vulnerability gate (.github/workflows/ci.yml) fails on any severity, so this blocks the build rather than just warning.

Fix

Enable central transitive pinning and pin AngleSharp to the patched 1.5.2 (latest stable; 1.5.3 is prerelease-only). No direct PackageReference needed — the pin flows through CPM.

Verification

  • dotnet list package --vulnerable --include-transitive → clean across all 10 projects.
  • AngleSharp resolves to 1.5.2 (type: CentralTransitive).
  • Blazor bUnit suite: 102/102 passing — API-compatible with bUnit's AngleSharp.Diffing.

The pin carries a comment noting it can be dropped once bUnit's chain resolves to ≥ 1.5.0 on its own.

bUnit -> AngleSharp.Diffing pulls AngleSharp 1.4.0 transitively, which
has a moderate mXSS advisory (GHSA-pgww-w46g-26qg / CVE-2026-54570)
patched in 1.5.0. The CI vulnerability gate fails on any severity, so
this blocks the build.

Enable central transitive pinning and pin AngleSharp to the patched
1.5.2 (latest stable). Verified: vuln scan clean across all projects,
Blazor bUnit suite 102/102 green.
@andregoepel
andregoepel merged commit 1bc0777 into main Jul 18, 2026
3 of 4 checks passed
@andregoepel
andregoepel deleted the fix/anglesharp-mxss-advisory branch July 18, 2026 02:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant